desktopproxy Utility to Abort or Cleanstop a BatchSolve

The desktopproxy Utility to abort or cleanstop a batch solve is available in the installation directory (.../AnsysEM/vxxx/Linux64 or ...\AnsysEM\vxxx\Win64).

To abort a job, run it on a host which has network access to the first execution host of the job, as well as has access to the directory of the project file. This utility does not abort Large scale DSO jobs for which you need to use desktopjob utility itself.

Usage:

desktopproxy -abort <projectpath>

-cleanstop <projectpath>

Where the <projectpath> is the full path to the project file.

The behavior (e.g., saving the results computed so far) should be same as if you interactively aborted AnsysEDT solve. if AnsysEDT is 'busy' (e.g., doing Optimetrics calculation, computing a report), abort (using desktopproxy) might take a long time.

The utility exits silently after it requests ansysedt process to abort the job cleanly. After the job ends, the batch log file may contain a message such as:

[error] Project:TestProject, Design:HFSSDesign1 (DrivenModal), Simulation was aborted by user on server: sjohpc-lsf-0.ansys.com. (3:52:30 PM Oct 11, 2013)

The lock file will be automatically deleted.

Example (Linux):

desktopproxy -abort /home/user/test/Diff_Via.aedt

Example (Windows):

desktopproxy -abort \\server\share\projectfolder\Diff_Via.aedt

Limitations:

• Aborting a job makes a best effort to delete all the temp directories on all the hosts
• For a hung job, a clean shutdown may not be possible. In that case, the user must use OS/scheduler's facilities to kill the job.